Method and apparatus for providing application notifications

ABSTRACT

An approach is provided for distributing notifications from developers to installed applications via a notification enabler separate from the applications. The notification platform determines at least one application installed on at least one device. Then, the notification platform causes, at least in part, a subscription via at least one notification enabler to one or more notification channels associated with the at least one application, wherein the at least one notification enabler is a separate component from the at least one application.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.13/665,516, filed Oct. 31, 2012, titled “Method and apparatus forproviding application notifications”, which is incorporated herein byreference in its entirety.

BACKGROUND

Service providers and device manufacturers (e.g., wireless, cellular,etc.) are continually challenged to deliver value and convenience toconsumers by, for example, providing compelling network services. Onearea of interest has been the development of distributing messages toapplications, including notifications. For example, push notificationsare essential for application developers to communicate with end userdevices. However, traditional push notifications require both serviceand client development. For example, each application must independentlyinclude services to support notifications. As a result, serviceproviders face significant challenges developing notification servicesindependently for individual applications.

SOME EXAMPLE EMBODIMENTS

Therefore, there is a need for an approach for distributingnotifications from developers to installed applications via a separatenotification enabler.

According to one embodiment, a method comprises determining at least oneapplication installed on at least one device. The method also comprisescausing, at least in part, a subscription via at least one notificationenabler to one or more notification channels associated with the atleast one application, wherein the at least one notification enabler isa separate component from the at least one application.

According to another embodiment, an apparatus comprises at least oneprocessor, and at least one memory including computer program code forone or more computer programs, the at least one memory and the computerprogram code configured to, with the at least one processor, cause, atleast in part, the apparatus to determine at least one applicationinstalled on at least one device. The apparatus is also caused to cause,at least in part, a subscription via at least one notification enablerto one or more notification channels associated with the at least oneapplication, wherein the at least one notification enabler is a separatecomponent from the at least one application.

According to another embodiment, a computer-readable storage mediumcarries one or more sequences of one or more instructions which, whenexecuted by one or more processors, cause, at least in part, anapparatus to determine at least one application installed on at leastone device. The apparatus is also caused to cause, at least in part, asubscription via at least one notification enabler to one or morenotification channels associated with the at least one application,wherein the at least one notification enabler is a separate componentfrom the at least one application.

According to another embodiment, an apparatus comprises means fordetermining at least one application installed on at least one device.The apparatus also comprises means for causing, at least in part, asubscription via at least one notification enabler to one or morenotification channels associated with the at least one application,wherein the at least one notification enabler is a separate componentfrom the at least one application.

In addition, for various example embodiments of the invention, thefollowing is applicable: a method comprising facilitating a processingof and/or processing (1) data and/or (2) information and/or (3) at leastone signal, the (1) data and/or (2) information and/or (3) at least onesignal based, at least in part, on (or derived at least in part from)any one or any combination of methods (or processes) disclosed in thisapplication as relevant to any embodiment of the invention.

For various example embodiments of the invention, the following is alsoapplicable: a method comprising facilitating access to at least oneinterface configured to allow access to at least one service, the atleast one service configured to perform any one or any combination ofnetwork or service provider methods (or processes) disclosed in thisapplication.

For various example embodiments of the invention, the following is alsoapplicable: a method comprising facilitating creating and/orfacilitating modifying (1) at least one device user interface elementand/or (2) at least one device user interface functionality, the (1) atleast one device user interface element and/or (2) at least one deviceuser interface functionality based, at least in part, on data and/orinformation resulting from one or any combination of methods orprocesses disclosed in this application as relevant to any embodiment ofthe invention, and/or at least one signal resulting from one or anycombination of methods (or processes) disclosed in this application asrelevant to any embodiment of the invention.

For various example embodiments of the invention, the following is alsoapplicable: a method comprising creating and/or modifying (1) at leastone device user interface element and/or (2) at least one device userinterface functionality, the (1) at least one device user interfaceelement and/or (2) at least one device user interface functionalitybased at least in part on data and/or information resulting from one orany combination of methods (or processes) disclosed in this applicationas relevant to any embodiment of the invention, and/or at least onesignal resulting from one or any combination of methods (or processes)disclosed in this application as relevant to any embodiment of theinvention.

In various example embodiments, the methods (or processes) can beaccomplished on the service provider side or on the mobile device sideor in any shared way between service provider and mobile device withactions being performed on both sides.

For various example embodiments, the following is applicable: Anapparatus comprising means for performing the method of any oforiginally filed claims 1-10, 21-30, and 46-48.

Still other aspects, features, and advantages of the invention arereadily apparent from the following detailed description, simply byillustrating a number of particular embodiments and implementations,including the best mode contemplated for carrying out the invention. Theinvention is also capable of other and different embodiments, and itsseveral details can be modified in various obvious respects, all withoutdeparting from the spirit and scope of the invention. Accordingly, thedrawings and description are to be regarded as illustrative in nature,and not as restrictive.

BRIEF DESCRIPTION OF THE DRAWINGS

The embodiments of the invention are illustrated by way of example, andnot by way of limitation, in the figures of the accompanying drawings:

FIG. 1 is a diagram of a system capable of distributing notificationsfrom developers to installed applications via a notification enablerseparate from the applications, according to one embodiment;

FIG. 2A is a diagram of the components of a notification platform,according to one embodiment;

FIG. 2B is a diagram of the components of a composer platform, accordingto one embodiment;

FIG. 3 is a flowchart of a process for distributing notifications fromdevelopers to installed applications via a notification enabler separatefrom the applications, according to one embodiment;

FIG. 4 is a flowchart of a process for distributing notifications fromdevelopers to installed applications via a notification enabler separatefrom the applications, according to one embodiment;

FIG. 5 is a flowchart of a process for distributing notifications fromdevelopers to installed applications via a notification enabler separatefrom the applications, according to one embodiment;

FIG. 6 is a flowchart of a process for distributing notifications fromdevelopers to installed applications via a notification enabler separatefrom the applications, according to one embodiment;

FIG. 7 is an illustration of the processes of FIGS. 3-6, according tovarious embodiments;

FIG. 8 is an illustration of the processes of FIGS. 3-6 from a userdevice viewpoint, according to various embodiments;

FIGS. 9A-9E are diagrams of user interfaces utilized in the processes ofFIGS. 3-6, according to various embodiments;

FIG. 10 is a diagram of hardware that can be used to implement anembodiment of the invention;

FIG. 11 is a diagram of a chip set that can be used to implement anembodiment of the invention; and

FIG. 12 is a diagram of a mobile terminal (e.g., handset) that can beused to implement an embodiment of the invention.

DESCRIPTION OF SOME EMBODIMENTS

Examples of a method, apparatus, and computer program for distributingnotifications from developers to installed applications via a separatenotification enabler are disclosed. In the following description, forthe purposes of explanation, numerous specific details are set forth inorder to provide a thorough understanding of the embodiments of theinvention. It is apparent, however, to one skilled in the art that theembodiments of the invention may be practiced without these specificdetails or with an equivalent arrangement. In other instances,well-known structures and devices are shown in block diagram form inorder to avoid unnecessarily obscuring the embodiments of the invention.

FIG. 1 is a diagram of a system capable of distributing notificationsfrom developers to installed applications via a notification enablerseparate from the applications, according to one embodiment.Applications are commonly used in devices, and each application isindividually configured to receive notifications, for instance by way ofan application programming interface (API). For example, before anapplication can receive notifications, it must register with anotification server. An application may then call a client API toregister itself and request a unique notification identifier. Thenotification identifier may be unique to the end user and application,and the notification server may rely on the notification identifier toroute notifications. The application then associates the notificationidentifier with a notification service associated with the application,thus informing the notification server of where to send notifications.To distribute a notification then, the developers send the notificationto the notification server using a service API, along with thenotification message itself as well as the notification identifier.Using the notification identifier, the notification server sends thenotification to the client application.

In this method, developers need to program push notification capabilityfor each application. The applications then independently push thenotifications to the user. In providing push notification capability,developers also need to include supporting functionalities includingregistration, notification service integration, etc. For example,pushing notifications to users may include sound, onscreen alert, or anicon denoting the presence of application notifications. Thus, oneproblem is continually requiring developers to equip applications withpush notification capability to applications, along with functionalitiessupporting push notification capability. Consequently, each applicationmay employ a different notification service or redundant APIs on boththe end user and client side.

To address this problem, a system 100 of FIG. 1 introduces thecapability to distribute notifications from developers to installedapplications via a notification enabler separate from the applications.In one embodiment, the system 100 thus eliminates at least a developerAPI such end users may receive messages for applications directly froman application channel, rather than requiring each end user to supportpush notification API communication with developer APIs to transmit eachmessage. In one embodiment, the notification enabler may subscribe adevice to an application notification channel.

For application notification channels, the system 100 may create one ormore notification channels associated with one or more applications. Inone embodiment, each application is associated with one notificationchannel. In another embodiment, each application may be associated withmultiple notification channels. For example, a game application may beassociated with one notification channel tailored to updates occurringin the game itself, another notification channel specifically forupdates in the application itself, and a third notification channelregarding other users in a social network group that may be active inthe game. For another example, each notification channel may alsopotentially serve multiple applications. For instance, a notificationchannel announcing updates may apply to all the applications associatedwith a particular application developer.

In one embodiment, the system 100 may provide a console, separate froman application, where publishers may send messages (includingnotifications) to the applications. Publishers may include any entitieswith authority to send messages relating to the applications. Forexample, publishers may include application owners, applicationdevelopers, or a combination thereof. In one embodiment, the consoleincludes a web console interface separate from application servers wherepublishers may easily compose a message. In one embodiment, the system100 may require the publisher to register and to verify that it is, infact, the publisher. Based on the publisher registration, the system 100may identify the publisher and thus provide the console withapplications associated with the publisher. For example, suchapplications may include all the applications made by a specificapplication developer or owned by a particular application owner. Theapplications may be fetched from an application database, for instance,an application store. Alternately, the system 100 may provide theapplications associated with the publisher, within a certain grouping.For example, a given application developer may have developedapplications that were games and news outlets. The system 100 may be setto retrieve only notifications relating to news outlets.

In one embodiment, the system 100 may create a channel for eachapplication to a notification server such that messages entered throughthe console may be sent to the applications. In one embodiment, thesystem 100 may distribute the messages to all the end users (or devices)that have installed the application. In another embodiment, the system100 may distribute the messages to end users that have subscribed to thechannels associated with the applications. For example, the system 100may prompt an application to subscribe to an application channel uponinstallation. Subscribing to the channel may permit a notificationenabler to retrieve a message published to the channel, and thus displaythe message at a mobile device.

In one embodiment, the system 100 may permit end users to choosesubscriptions and subscription settings. For example, upon installationof an application, the system 100 may prompt an end user to selectwhether or not to subscribe to a channel to receive notifications fromthe application. In one scenario, the prompt may take the form of an“acceptance” window. In another example, the system 100 may prompt theend user to select whether or not to subscribe upon the firstnotification. For instance, an application may be installed on a userdevice for a period of time before a developer sends an updatenotification. Then, the system 100 may route the update notificationthrough the channel to an application installed on a device, at whichpoint the system 100 may create an “acceptance” window for the end userto select whether or not to continue to receive notifications.

In one embodiment, the initial acceptance window may include a requestfor preference information associated with the messages, subscription,or a combination thereof. For example, the system 100 may prompt endusers to select message frequency, message type, message displayoptions, or a combination thereof. Message frequency may refer to howoften the end user may permit notifications from an application channel,for instance daily, weekly, monthly, etc. Message type may includetext-only messages, rich notification messages, or a combinationthereof. Message display options may pertain to whether the message is apop-up overlaid on the screen, as a scrolling line, a small previewwindow, etc. In one embodiment, system 100 may also integrate displayoptions with notification services available at the end user devicesand/or applications with API for supporting notifications.

In one embodiment, the system 100 may determine contextual informationassociated with notification channels, end user device, applications, ora combination thereof. For example, contextual information may includetechnical specifications including available bandwidth or type ofnotifications supported. In such a scenario, a given channel may bedevoted to text-only messages for low bandwidth devices and/or settings.Alternately, contextual information may include information such aslocation information associated with devices. Then, the system 100 mayhelp developers target notifications, for example, to a certaingeographic area. Other contextual information along these lines mayinclude user profile information, user device activity information, or acombination thereof.

In a further embodiment, the system 100 may further target messages andnotifications by profiling end users. For example, the system 100 mayprofile users according to attributes associated with applications (orgroups of applications) installed on devices associated with the users.The system 100 may also profile users according to user interaction withnotifications. In one scenario, the system 100 may determine that agiven user does not respond to notifications, whereas another user tendsto frequently click on links or media offered in notifications. Thesystem 100 may then send notifications more frequently to the seconduser, rather than the first.

As shown in FIG. 1, the system 100 comprises a user equipment (UE) 101having connectivity to an application 103, a notification enabler 107, auser interface module 109, a notification platform 111, a composerplatform 113, and an application database 115 via a communicationnetwork 105. By way of example, the communication network 105 of system100 includes one or more networks such as a data network, a wirelessnetwork, a telephony network, or any combination thereof. It iscontemplated that the data network may be any local area network (LAN),metropolitan area network (MAN), wide area network (WAN), a public datanetwork (e.g., the Internet), short range wireless network, or any othersuitable packet-switched network, such as a commercially owned,proprietary packet-switched network, e.g., a proprietary cable orfiber-optic network, and the like, or any combination thereof. Inaddition, the wireless network may be, for example, a cellular networkand may employ various technologies including enhanced data rates forglobal evolution (EDGE), general packet radio service (GPRS), globalsystem for mobile communications (GSM), Internet protocol multimediasubsystem (IMS), universal mobile telecommunications system (UMTS),etc., as well as any other suitable wireless medium, e.g., worldwideinteroperability for microwave access (WiMAX), Long Term Evolution (LTE)networks, code division multiple access (CDMA), wideband code divisionmultiple access (WCDMA), wireless fidelity (WiFi), wireless LAN (WLAN),Bluetooth®, Internet Protocol (IP) data casting, satellite, mobilead-hoc network (MANET), and the like, or any combination thereof.

The UE 101 is any type of mobile terminal, fixed terminal, or portableterminal including a mobile handset, station, unit, device, multimediacomputer, multimedia tablet, Internet node, communicator, desktopcomputer, laptop computer, notebook computer, netbook computer, tabletcomputer, personal communication system (PCS) device, personalnavigation device, personal digital assistants (PDAs), audio/videoplayer, digital camera/camcorder, positioning device, televisionreceiver, radio broadcast receiver, electronic book device, game device,or any combination thereof, including the accessories and peripherals ofthese devices, or any combination thereof. It is also contemplated thatthe UE 101 can support any type of interface to the user (such as“wearable” circuitry, etc.).

In one embodiment, the application 103 is any application installed on adevice, including UE 101. In one embodiment, the application 103 may bein connectivity with the notification enabler 107 such that thenotification enabler 107 may relate to the notification platform 111that application 103 has been installed successfully at UE 101. In oneembodiment, the notification enabler 107 may even participate in theinstallation of application 103, where applications that are installedwith the aid of notification enabler 107 are in contact withnotification platform 111. In another embodiment, notification enabler107 may simply determine that an application, including application 103,has been installed on UE 101, and then notify notification platform 111of the installation. In one embodiment, user interface module 109 mayaid in displaying notifications and/or initial subscription “acceptance”messages where the notification platform 111 may prompt the user toestablish settings associated with notification channel subscriptions ordisplays. For example, the notification enabler 107 may work with theuser interface module 109 to prompt the user to establish settings uponinstallation. In another example, the notification enabler 107 may trackthe number of application installations and initiate subscriptionsetting prompts only after a predefined number of installations havebeen successful.

In one embodiment, the notification enabler 107 may subscribeapplication 103 (and UE 101) to the notification platform 111, where thenotification platform 111 may then distribute messages to channelsmanaged by the composer platform 113. In one embodiment, thenotification platform 111 may manage channel subscriptions, wheresubscribing UEs 101 and applications 103 may receive messagesdistributed to the channels. In one embodiment, composer platform 113may create and establish the notification channels. In one embodiment,the composer platform 113 may maintain one channel per application. Inanother embodiment, the composer platform 113 may create one or morechannels associated with one or more applications. In one embodiment, UE101 and application 103 subscription to the notification platform 111may include the notification enabler 107 registering the UE 101 andapplication 103 to the notification platform 111. Such registration mayinclude obtaining an application identifier associated with application103 and a device identifier associated with UE 101, or a combinationthereof. Notification platform 111 may then route messages from thecomposer platform 113 based on the registration. For example,notification platform 111 may route messages to the UE 101 based onsettings established by the notification enabler 107 at the notificationplatform 111 during the initial “acceptance” messages.

In one embodiment, the composer platform 113 may allow publishers tosend messages (including notifications) to the applications 103 viachannels managed by the composer platform 113, connected to UEs 101 viachannel subscriptions created at the notification platform 111. In otherwords, the system 100 may send publisher messages over a connectionbetween a notification backend (including the notification enabler 107and notification platform 111) and the composer backend (including thecomposer platform 113). In one embodiment, the composer platform 113 mayprovide publishers with a console interface. For example, one or moreconsole interfaces may be associated with at least one application. Theconsole interface may include a web console interface where publishersmay easily create and design messages without application APIs developedfor each application. The UE 101 may then route the message to theapplication 103, where the user interface module 109 then displays themessage.

In one embodiment, the application database 115 may manage all theapplications available, for instance, in an applications store. Then,the composer platform 113 may interact with the application database 115to form notification channels associated with the applications, ormodify notification channels according to changes in the applicationsstored in the application database 115. In one embodiment, theapplication database 115 may also organize the applications. Forexample, the application database 115 may categorize the applications,for instance, by associated application developers, application owners,publishers, devices installed, or a combination thereof.

By way of example, the UE 101, application 103, notification enabler107, user interface module 109, notification platform 111, composerplatform 113, and application database 115 communicate with each otherand other components of the communication network 105 using well known,new or still developing protocols. In this context, a protocol includesa set of rules defining how the network nodes within the communicationnetwork 105 interact with each other based on information sent over thecommunication links. The protocols are effective at different layers ofoperation within each node, from generating and receiving physicalsignals of various types, to selecting a link for transferring thosesignals, to the format of information indicated by those signals, toidentifying which software application executing on a computer systemsends or receives the information. The conceptually different layers ofprotocols for exchanging information over a network are described in theOpen Systems Interconnection (OSI) Reference Model.

Communications between the network nodes are typically effected byexchanging discrete packets of data. Each packet typically comprises (1)header information associated with a particular protocol, and (2)payload information that follows the header information and containsinformation that may be processed independently of that particularprotocol. In some protocols, the packet includes (3) trailer informationfollowing the payload and indicating the end of the payload information.The header includes information such as the source of the packet, itsdestination, the length of the payload, and other properties used by theprotocol. Often, the data in the payload for the particular protocolincludes a header and payload for a different protocol associated with adifferent, higher layer of the OSI Reference Model. The header for aparticular protocol typically indicates a type for the next protocolcontained in its payload. The higher layer protocol is said to beencapsulated in the lower layer protocol. The headers included in apacket traversing multiple heterogeneous networks, such as the Internet,typically include a physical (layer 1) header, a data-link (layer 2)header, an internetwork (layer 3) header and a transport (layer 4)header, and various application (layer 5, layer 6 and layer 7) headersas defined by the OSI Reference Model.

FIG. 2A is a diagram of the components of the notification platform 111,according to one embodiment. By way of example, the notificationplatform 111 includes one or more components for providing notificationdistribution via a separate notification enabler by keeping track ofmobile device subscriptions to notification channels. It is contemplatedthat the functions of these components may be combined in one or morecomponents or performed by other components of equivalent functionality.In this embodiment, the notification platform 111 includes anapplication module 203, registration module 205, subscription module207, and publisher module 209. The control logic 201 executes at leastone algorithm for executing functions at the notification platform 111.

In one embodiment, the control logic 201 may determine the subscriptionsbetween application channels and applications installed on mobiledevices. In one embodiment, the control logic 201 and application module203 may determine at least one application installed on at least onedevice. For example, the notification enabler 107 may contact thecontrol logic 201 and application module 203 upon successfulinstallation of at least one application. In one embodiment, the controllogic 201 and application module 203 may identify the application in theapplication database 115 and/or associated applications. In oneembodiment, the control logic 201 and registration module 205 may thencause a registration of at least on application identifier associatedwith the application, at least one device identifier associated with atleast one device, or a combination thereof, where routing of messagesover notification channels is based on the registration. For instance,each application may be associated with one application identifier andone notification channel. In this case then, registering a deviceidentifier with the notification channel associated with the oneapplication identifier may permit messages from the one application tobe routed to the one device (associated with the one device identifier),over the notification channel. Alternately, several devices (denoted byseveral device identifiers) may register under one applicationidentifier since the application was installed on all the devices. Thecontrol logic 201 and registration module 205 may then route messagesvia notification channels associated with the application, to all theregistered devices. In another embodiment, application identifiers maybe unique to each application installed on each device. Then, thecontrol logic 201 and registration module 205 may register eachapplication identifier to an associated application notification channelto receive messages.

In one embodiment, the control logic 201 and subscription module 207contain and manage the various subscriptions associated with theregistration. For example, the control logic 201 and subscription module207 may cause a subscription to notification channels associated with atleast one application, at least one device, and/or groupings ofapplications or devices. In one embodiment, the control logic 201 andsubscription module 207 may initiate subscription or registration (withthe help of the registration module 205) when a number of installationshave been successful. For example, the control logic 201 may establish apredefined number of installations, where the notification enabler 107may communicate with the control logic 201 and application module 203upon reaching a given number of successful installations. One suchscenario may include where notification enabler 107 has successfullyinstalled a pre-set number of applications associated with a particularapplication owner, developer, or publisher. Another such scenario mayinclude where control logic 201 and application module 203 determinethat a given application has been installed at a pre-set number ofdevices.

In one embodiment, the control logic 201 and subscription module 207 maydetermine settings associated with the subscriptions. For example, thecontrol logic 201 and subscription module 207 may determine that one ormore messages routed to a given device constitutes an initial message,and thus cause a request for preference information associated withmessages, the subscription to channels, or a combination thereof. Forexample, the control logic 201 and subscription module 207 may prompt,via a user interface presentation, the selection of settings includingmessage frequency, subscription to one or more channels, types ofmessages receivable (text, image, video, etc.), or a combinationthereof. The control logic 201 and subscription module 207 may thenmanage the individualized subscriptions that various applications and/ordevices maintain with various notification channels.

In another embodiment, the control logic 201 and publisher module 209may retrieve a message from the composer platform 113, and publish themessage at the associated devices and installed applications via thenotification channel. In one embodiment, the control logic 201 andpublisher module 209 may take into account notification services alreadyavailable in the devices and applications. For example, the controllogic 201 and publisher module 209 may ensure that the message receivedfrom the composer platform 113 is compatible with the receiving devicesand applications. As previously discussed, the user interface module 109may cause the application to show the message on the device interface.In a further embodiment, the control logic 201, subscription module 207,and publisher module 209 may monitor interactions with the notificationsas received from the UEs 101 and adjust subscription settings and/ornotifications based on the monitoring.

FIG. 2B is a diagram of the components of the composer platform 113,according to one embodiment. By way of example, the composer platform113 includes one or more components for providing notification channels.It is contemplated that the functions of these components may becombined in one or more components or performed by other components ofequivalent functionality. In this embodiment, the composer platform 113includes publisher module 213, a validation module 215, a channel module217, and a message module 219. The control logic 201 executes at leastone algorithm for executing functions at the composer platform 113.

In one embodiment, the controller 211 and publisher module 213 mayfetch, from the application database 115, all the applicationsassociated with one or more entities with authorization to send messagesto the applications. The entities may be, for example, applicationowners, application developers, application publishers, or a combinationthereof. For instance, the application developer may sign into aninterface where the controller 211 and publisher module 213 mayrecognize the application owner as being the developer of one or moreother applications. In one embodiment, the controller 211 and validationmodule 215 may seek verification from the developer to certifyauthorization to distribute messages to the associated application. Forexample, the controller 211 and validation module 215 may require loginand password information to certify that a registrant is, in fact, theapplication developer.

In one embodiment, the controller 211 and channel module 217 may thencreate one or more channels based, at least in part, on applicationsidentified as associated with the one or more given owners, includingapplications given by the application database 115. In one embodiment,the one or more channels are notification channels for distributingnotifications from application developers to end users and mobiledevices where associated applications are installed. For example, thecontroller 211 may create notification channels based, at least in part,on identification of at least one application, publishers associatedwith the at least one application, or a combination through anapplication store. For such a case, there may be one or more channelsfor every identified application, for instance, the controller 211 andchannel module 217 may create one or more channels associated with everyapplication in application database 115. For another instance, thecontroller 211 and channel module 217 may create channels based onvalidation of one or more publishers based on the identification, atleast one application store, or a combination thereof. In one such case,the controller 211 and channel module 217 may create a channel for eachof the applications found to be attributable to the validatedpublishers. In other words, the controller 211 and channel module 217may create groupings of applications and create channels according tothe groupings.

Furthermore, the controller 211 and channel module 217 may cause anassociation of contextual criteria with the notification channels. Forinstance, notification channels may be created based on contextualcriteria, including bandwidth, notification type (push or richnotifications), content (text, image, or video), or a combinationthereof. In another embodiment, the controller 211 and channel module217 may cause, at least in part, routing of messages over thenotification channels based, at least in part, on whether contextualinformation associated with the at least one device, the at least oneapplication, or a combination thereof at least substantially meets theone or more contextual criteria. For example, controller 211 maydetermine from contextual information associated with at least onedevice, that the device does not have adequate bandwidth to receive agiven message. In this case, the controller 211 and channel module 217may employ a comparable message over another notification channelassociated with messages that require less bandwidth.

In one embodiment, the controller 211 and message module 219 may createa console interface for the publisher to enter his message. In oneinstance, the console interface may include, at least in part, a webconsole interface separate from one or more application serversassociated with at least one application. For example, without directlyaccessing an application, a publisher may enter the console interface,validate his identify as a publisher via the interface (and publishermodule 213), and compose a notification that may then be distributed viathe channels created by the channel module 217.

FIG. 3 is a flowchart of a process for distributing notifications fromdevelopers to installed applications via a separate notificationenabler, according to one embodiment. In one embodiment, thenotification platform 111 performs the process 300 and is implementedin, for instance, a chip set including a processor and a memory as shownin FIG. 11. In step 301, the control logic 201 may determine at leastone application installed on at least one device. Based on theapplication, the control logic 201 may determine one or morenotification channels associated with the at least one application (step303). Upon determining one or more notification channels associated withthe at least one application, the control logic 201 may cause, at leastin part, a subscription via at least one notification enabler to one ormore notification channels associated with the at least one application,wherein the at least one notification enabler is a separate componentfrom the at least one application (steps 305-307). For instance, thecontrol logic 201 may determine notification channels associated with anapplication, and connect UEs 101 to the channels via subscriptions. Forexample, notification enabler 107 subscriptions to a notificationchannel at notification platform 111 may permit control logic 201 andnotification enabler 107 to retrieve messages published to the channels.

FIG. 4 is a flowchart of a process for creating subscriptions tonotification channels, according to one embodiment. In one embodiment,the notification enabler 107 performs the process 400 and is implementedin, for instance, a chip set including a processor and a memory as shownin FIG. 11. In one embodiment, the notification enabler 107 may cause,at least in part, a registration of at least one application identifierassociated with the at least one application, at least one deviceidentifier associated with the at least one device, or a combinationthereof; and cause, at least in part, a routing of one or more messagesover the one or more notification channels based, at least in part, onthe registration (steps 401-407). For example, the notification enabler107 may request specific identifiers from the device and application toconstruct subscriptions according to user specifications. As previouslydiscussed, users may specify particular settings, including notificationfrequency, type, etc. The notification enabler 107 may create distinctsubscriptions identified via the registration information includingapplication and device identifiers.

FIG. 5 is a flowchart of a process for distributing messages frompublishers according to user settings and preferences, according to oneembodiment. In one embodiment, the notification platform 111 performsthe process 500 and is implemented in, for instance, a chip setincluding a processor and a memory as shown in FIG. 11. In oneembodiment, the control logic 201 may cause, at least in part, apresentation of the one or more messages in a notification userinterface associated with the at least one notification enabler. Indoing so, the control logic 201 may determine that the one or moremessages include, at least in part, one or more initial messages routedto the at least one application, the at least one device, or acombination thereof (step 501). For example, control logic 201 maydetermine that a message will be the first message a UE 101 will bereceiving from a given application since the UE 101 and application wereregistered to subscribe to the application notification channel. Then,the control logic 201 may cause, at least in part, a request forpreference information associated with the one or more messages, thesubscription to the one or more notification channels, or a combinationthereof, wherein the one or more messages is based, at least in part, onthe preference information (steps 503-505). In one embodiment, thecontrol logic 201 may pair preference information with registrationinformation such that preferences indicated for a specific device, areassociated with the device and applied for relevant applicationnotification distribution.

In one embodiment, the subsequent presentation of messages may includethe control logic 201 receiving the one or more messages via a consoleinterface presented to one or more publishers associated with the atleast one application. In one embodiment, the console interface may bewherein the console interface includes, at least in part, a web consoleinterface that is separate from one or more application serversassociated with the at least one application (step 507).

FIG. 6 is a flowchart of creating channels in accordance with publisherinformation and contextual criteria, according to one embodiment. In oneembodiment, the composer platform 113 performs the process 600 and isimplemented in, for instance, a chip set including a processor and amemory as shown in FIG. 11. In one embodiment, the controller 211 maycause, at least in part, an identification of the at least oneapplication, one or more publishers associated with the at least oneapplication, or a combination thereof through at least one applicationstore and cause, at least in part, a creation of the one or morenotification channels based, at least in part, the identification (step601). The controller 211 may also cause, at least in part, a validationof the one or more publishers based, at least in part, on theidentification, the at least one application store, or a combinationthereof, wherein the creation of the one or more notification channelsis further based, at least in part, on the validation (steps 603-605).Additionally, the controller 211 may cause, at least in part, anassociation of one or more contextual criteria with the one or morenotification channels (step 607). As previously discussed, thecontroller 211 may determine contextual criteria associated with thenotification channels, UEs 101, or applications. For example, controller211 may determine location information associated with the UEs 101 andtarget messages according to the location information. In anotherexample, controller 211 may profile users based on installedapplications and tailor messages according to the profiles. Thus forstep 607, the controller 211 may cause, at least in part, a routing ofone or more messages over the one or more notification channels based,at least in part, on whether contextual information associated with theat least one device, the at least one application, or a combinationthereof at least substantially meets the one or more contextualcriteria.

FIGS. 7 and 8 are illustrations of the processes of FIG. 3, according tovarious embodiments. FIG. 7 shows one embodiment where publishers 703may initiate use of a composer 705, including a composer like thecomposer platform 113. To help publishers 703 in constructing theirmessage, the composer 705 may interact with an application database, forexample, application store 707. For instance, composer 705 may fetch allthe applications associated with given publishers 703, from applicationstore 707.

Mobile device 709 may have installed on it, application 711 a and 711 b.In one embodiment, the composer 705 may then create a channel 713 a frominstalled application 711 a to the notification server 713. In oneembodiment, the composer 705 creates a channel for each application,creating channels 713 a and 713 b. The notification enabler 715 may thensubscribe the installed applications to associated channels. Forexample, the notification enabler 715 may subscribe installedapplication 711 a to associated channel 713 a and installed application711 b has one associated channel 713 b. The notification server 717 maymanage all the subscriptions of installed applications, to associatedapplication channels.

The composer 705 may then publish messages to the notification server717, from which a notification enabler 715 may retrieve the messages,based on its subscriptions to the notification server 717. In this way,the publishers 703 may send notifications to all the end user devices709 that have installed the applications, and channel subscriptions arecentralized in the notification server 717 rather than individualapplication APIs.

FIG. 8 shows one embodiment where a user installs an application 801 andenabler 803 receives notification that installation was successful.Then, the enabler 803 may subscribe the user to a correspondingapplication channel at notification backend 805. The channel may involvethe composer backend 807 noting all the installed applications, andcreating a notification for all the installed applications (or all thecustomers that have installed the application). After creating thenotification, the composer backend 807 may publish the notification tothe channel. In one scenario, the notification may be the firstnotification 809 the user receives from the application. In this case,the first notification 809 may include an acceptance or confirmationwindow 811 where the user may choose whether to subscribe to theapplication channel. Should the user elect to subscribe, the composednotification 813 may be displayed to the user. In one embodiment, thecomposed notification 813 may include rich notifications and includelinks, video, maps, etc.

FIGS. 9A-9E are diagrams of user interfaces utilized in the processes ofFIG. 3, according to various embodiments. FIG. 9A is a diagram of aconsole interface 900 for composing one or more messages. For oneembodiment, this interface may be a web console interface separate fromapplication servers associated with applications. For example, thecomposer platform 113 may provide the console may provide independentlyonline, eliminating the need for each application to have its own APIfor notifications. In one embodiment, the console interface 900 mayinclude a drop-down menu 901 to select an application or group ofapplications where the message is directed. For example, the drop-downmenu may include applications with associated application channels.Next, console interface 900 may provide a title line 903. In oneembodiment, the title line 903 may have a maximum character length. Inone embodiment, the content of the title line 903 may help publisherscategorize or organize messages. For example, the console interface 900may permit publishers to re-use messages or compile a set of messagetemplates or standard messages. In one instance, console interface 900may permit publishers to search for these methods using the title.Message box 905 may provide publishers a space to create their messages.In one embodiment, message box 905 may include a character counter.Further message customization may be available via button options 907where publishers may opt to add buttons or additional functionality tothe message and name the buttons. Application identifier 909 may providefurther fine-grain selection of applications. For example, differentversions of an application may be denoted by different applicationidentifiers. Entering a particular identifier may permit publishers tofurther target message distribution. Preview 911 may display a versionof how users see the notification. Pricing information 913 may also bepart of the console interface 900. The console interface 900 may includemore than one page of options. Page button 915 may permit publishers tomove on to more message creation options.

FIG. 9B is a further diagram 920 of a console interface 900 forcomposing one or more messages. In one embodiment, the console interface920 may include timing options 921 for example, for sending immediately,or setting a future time. The timing options 921 may then offer calendar923. Upon message completion, console interface 920 may permit furtherpublication options 925, including modifying the message (by revisitingconsole interface 900), saving the message as a draft, or sending.

FIG. 9C is a diagram of a user interface 930 for composing one or moremessages. For example, the user interface 930 may include a list ofnotifications 931. The list 931 may include application names,application icons 933, or a combination thereof for immediateidentification of the applications. In one embodiment, the list 931 mayalso include an abbreviated version 935 of the message. For example, theabbreviated version may be the title of the message. In anotherembodiment, the list 931 may show a caption 937 representing that thereare multiple notifications. For example, list 931 may display caption937 when there is more than one message from the application.

FIG. 9D is a diagram of a display 940 for one or more messages. Thedisplay 940 may include the application name and icon 941, as well asthe title 943 of the message. Message text 945 may be displayed in thecenter of the screen, along with a prompt 947 for the user. FIG. 9E is adiagram 950 of an alternate display 950 for one or more messages. Here,the display 950 may include only an application icon 951 along with anabbreviated message, for instance, the message title 953. The display950 may include prompts 955 for the user to see the full message, orexit. In contrast to display 940, display 950 may not take up the entirescreen.

The processes described herein for distributing notifications fromdevelopers to installed applications via a notification enabler separatefrom the applications may be advantageously implemented via software,hardware, firmware or a combination of software and/or firmware and/orhardware. For example, the processes described herein, may beadvantageously implemented via processor(s), Digital Signal Processing(DSP) chip, an Application Specific Integrated Circuit (ASIC), FieldProgrammable Gate Arrays (FPGAs), etc. Such exemplary hardware forperforming the described functions is detailed below.

FIG. 10 illustrates a computer system 1000 upon which an embodiment ofthe invention may be implemented. Although computer system 1000 isdepicted with respect to a particular device or equipment, it iscontemplated that other devices or equipment (e.g., network elements,servers, etc.) within FIG. 10 can deploy the illustrated hardware andcomponents of system 1000. Computer system 1000 is programmed (e.g., viacomputer program code or instructions) to initiate a call using amultiple antenna system as described herein and includes a communicationmechanism such as a bus 1010 for passing information between otherinternal and external components of the computer system 1000.Information (also called data) is represented as a physical expressionof a measurable phenomenon, typically electric voltages, but including,in other embodiments, such phenomena as magnetic, electromagnetic,pressure, chemical, biological, molecular, atomic, sub-atomic andquantum interactions. For example, north and south magnetic fields, or azero and non-zero electric voltage, represent two states (0, 1) of abinary digit (bit). Other phenomena can represent digits of a higherbase. A superposition of multiple simultaneous quantum states beforemeasurement represents a quantum bit (qubit). A sequence of one or moredigits constitutes digital data that is used to represent a number orcode for a character. In some embodiments, information called analogdata is represented by a near continuum of measurable values within aparticular range. Computer system 1000, or a portion thereof,constitutes a means for performing one or more steps distributingnotifications from developers to installed applications via anotification enabler separate from the applications.

A bus 1010 includes one or more parallel conductors of information sothat information is transferred quickly among devices coupled to the bus1010. One or more processors 1002 for processing information are coupledwith the bus 1010.

A processor (or multiple processors) 1002 performs a set of operationson information as specified by computer program code relateddistributing notifications from developers to installed applications viaa notification enabler separate from the applications. The computerprogram code is a set of instructions or statements providinginstructions for the operation of the processor and/or the computersystem to perform specified functions. The code, for example, may bewritten in a computer programming language that is compiled into anative instruction set of the processor. The code may also be writtendirectly using the native instruction set (e.g., machine language). Theset of operations include bringing information in from the bus 1010 andplacing information on the bus 1010. The set of operations alsotypically include comparing two or more units of information, shiftingpositions of units of information, and combining two or more units ofinformation, such as by addition or multiplication or logical operationslike OR, exclusive OR (XOR), and AND. Each operation of the set ofoperations that can be performed by the processor is represented to theprocessor by information called instructions, such as an operation codeof one or more digits. A sequence of operations to be executed by theprocessor 1002, such as a sequence of operation codes, constituteprocessor instructions, also called computer system instructions or,simply, computer instructions. Processors may be implemented asmechanical, electrical, magnetic, optical, chemical or quantumcomponents, among others, alone or in combination.

Computer system 1000 also includes a memory 1004 coupled to bus 1010.The memory 1004, such as a random access memory (RAM) or any otherdynamic storage device, stores information including processorinstructions for distributing notifications from developers to installedapplications via a notification enabler separate from the applications.Dynamic memory allows information stored therein to be changed by thecomputer system 1000. RANI allows a unit of information stored at alocation called a memory address to be stored and retrievedindependently of information at neighboring addresses. The memory 1004is also used by the processor 1002 to store temporary values duringexecution of processor instructions. The computer system 1000 alsoincludes a read only memory (ROM) 1006 or any other static storagedevice coupled to the bus 1010 for storing static information, includinginstructions, that is not changed by the computer system 1000. Somememory is composed of volatile storage that loses the information storedthereon when power is lost. Also coupled to bus 1010 is a non-volatile(persistent) storage device 1008, such as a magnetic disk, optical diskor flash card, for storing information, including instructions, thatpersists even when the computer system 1000 is turned off or otherwiseloses power.

Information, including instructions for distributing notifications fromdevelopers to installed applications via a notification enabler separatefrom the applications, is provided to the bus 1010 for use by theprocessor from an external input device 1012, such as a keyboardcontaining alphanumeric keys operated by a human user, a microphone, anInfrared (IR) remote control, a joystick, a game pad, a stylus pen, atouch screen, or a sensor. A sensor detects conditions in its vicinityand transforms those detections into physical expression compatible withthe measurable phenomenon used to represent information in computersystem 1000. Other external devices coupled to bus 1010, used primarilyfor interacting with humans, include a display device 1014, such as acathode ray tube (CRT), a liquid crystal display (LCD), a light emittingdiode (LED) display, an organic LED (OLED) display, a plasma screen, ora printer for presenting text or images, and a pointing device 1016,such as a mouse, a trackball, cursor direction keys, or a motion sensor,for controlling a position of a small cursor image presented on thedisplay 1014 and issuing commands associated with graphical elementspresented on the display 1014. In some embodiments, for example, inembodiments in which the computer system 1000 performs all functionsautomatically without human input, one or more of external input device1012, display device 1014 and pointing device 1016 is omitted.

In the illustrated embodiment, special purpose hardware, such as anapplication specific integrated circuit (ASIC) 1020, is coupled to bus1010. The special purpose hardware is configured to perform operationsnot performed by processor 1002 quickly enough for special purposes.Examples of ASICs include graphics accelerator cards for generatingimages for display 1014, cryptographic boards for encrypting anddecrypting messages sent over a network, speech recognition, andinterfaces to special external devices, such as robotic arms and medicalscanning equipment that repeatedly perform some complex sequence ofoperations that are more efficiently implemented in hardware.

Computer system 1000 also includes one or more instances of acommunications interface 1070 coupled to bus 1010. Communicationinterface 1070 provides a one-way or two-way communication coupling to avariety of external devices that operate with their own processors, suchas printers, scanners and external disks. In general the coupling iswith a network link 1078 that is connected to a local network 1080 towhich a variety of external devices with their own processors areconnected. For example, communication interface 1070 may be a parallelport or a serial port or a universal serial bus (USB) port on a personalcomputer. In some embodiments, communications interface 1070 is anintegrated services digital network (ISDN) card or a digital subscriberline (DSL) card or a telephone modem that provides an informationcommunication connection to a corresponding type of telephone line. Insome embodiments, a communication interface 1070 is a cable modem thatconverts signals on bus 1010 into signals for a communication connectionover a coaxial cable or into optical signals for a communicationconnection over a fiber optic cable. As another example, communicationsinterface 1070 may be a local area network (LAN) card to provide a datacommunication connection to a compatible LAN, such as Ethernet. Wirelesslinks may also be implemented. For wireless links, the communicationsinterface 1070 sends or receives or both sends and receives electrical,acoustic or electromagnetic signals, including infrared and opticalsignals, that carry information streams, such as digital data. Forexample, in wireless handheld devices, such as mobile telephones likecell phones, the communications interface 1070 includes a radio bandelectromagnetic transmitter and receiver called a radio transceiver. Incertain embodiments, the communications interface 1070 enablesconnection to the communication network 105 for distributingnotifications from developers to installed applications via anotification enabler separate from the applications to the UE 101.

The term “computer-readable medium” as used herein refers to any mediumthat participates in providing information to processor 1002, includinginstructions for execution. Such a medium may take many forms,including, but not limited to computer-readable storage medium (e.g.,non-volatile media, volatile media), and transmission media.Non-transitory media, such as non-volatile media, include, for example,optical or magnetic disks, such as storage device 1008. Volatile mediainclude, for example, dynamic memory 1004. Transmission media include,for example, twisted pair cables, coaxial cables, copper wire, fiberoptic cables, and carrier waves that travel through space without wiresor cables, such as acoustic waves and electromagnetic waves, includingradio, optical and infrared waves. Signals include man-made transientvariations in amplitude, frequency, phase, polarization or otherphysical properties transmitted through the transmission media. Commonforms of computer-readable media include, for example, a floppy disk, aflexible disk, hard disk, magnetic tape, any other magnetic medium, aCD-ROM, CDRW, DVD, any other optical medium, punch cards, paper tape,optical mark sheets, any other physical medium with patterns of holes orother optically recognizable indicia, a RAM, a PROM, an EPROM, aFLASH-EPROM, an EEPROM, a flash memory, any other memory chip orcartridge, a carrier wave, or any other medium from which a computer canread. The term computer-readable storage medium is used herein to referto any computer-readable medium except transmission media.

Logic encoded in one or more tangible media includes one or both ofprocessor instructions on a computer-readable storage media and specialpurpose hardware, such as ASIC 1020.

Network link 1078 typically provides information communication usingtransmission media through one or more networks to other devices thatuse or process the information. For example, network link 1078 mayprovide a connection through local network 1080 to a host computer 1082or to equipment 1084 operated by an Internet Service Provider (ISP). ISPequipment 1084 in turn provides data communication services through thepublic, world-wide packet-switching communication network of networksnow commonly referred to as the Internet 590.

A computer called a server host 1092 connected to the Internet hosts aprocess that provides a service in response to information received overthe Internet. For example, server host 1092 hosts a process thatprovides information representing video data for presentation at display1014. It is contemplated that the components of system 1000 can bedeployed in various configurations within other computer systems, e.g.,host 1082 and server 1092.

At least some embodiments of the invention are related to the use ofcomputer system 1000 for implementing some or all of the techniquesdescribed herein. According to one embodiment of the invention, thosetechniques are performed by computer system 500 in response to processor1002 executing one or more sequences of one or more processorinstructions contained in memory 1004. Such instructions, also calledcomputer instructions, software and program code, may be read intomemory 1004 from another computer-readable medium such as storage device1008 or network link 1078. Execution of the sequences of instructionscontained in memory 1004 causes processor 1002 to perform one or more ofthe method steps described herein. In alternative embodiments, hardware,such as ASIC 1020, may be used in place of or in combination withsoftware to implement the invention. Thus, embodiments of the inventionare not limited to any specific combination of hardware and software,unless otherwise explicitly stated herein.

The signals transmitted over network link 1078 and other networksthrough communications interface 1070, carry information to and fromcomputer system 1000. Computer system 1000 can send and receiveinformation, including program code, through the networks 1080, 1090among others, through network link 1078 and communications interface1070. In an example using the Internet 1090, a server host 1092transmits program code for a particular application, requested by amessage sent from computer 1000, through Internet 1090, ISP equipment1084, local network 1080 and communications interface 1070. The receivedcode may be executed by processor 1002 as it is received, or may bestored in memory 1004 or in storage device 1008 or any othernon-volatile storage for later execution, or both. In this manner,computer system 1000 may obtain application program code in the form ofsignals on a carrier wave.

Various forms of computer readable media may be involved in carrying oneor more sequence of instructions or data or both to processor 1002 forexecution. For example, instructions and data may initially be carriedon a magnetic disk of a remote computer such as host 1082. The remotecomputer loads the instructions and data into its dynamic memory andsends the instructions and data over a telephone line using a modem. Amodem local to the computer system 1000 receives the instructions anddata on a telephone line and uses an infra-red transmitter to convertthe instructions and data to a signal on an infra-red carrier waveserving as the network link 1078. An infrared detector serving ascommunications interface 1070 receives the instructions and data carriedin the infrared signal and places information representing theinstructions and data onto bus 1010. Bus 1010 carries the information tomemory 1004 from which processor 1002 retrieves and executes theinstructions using some of the data sent with the instructions. Theinstructions and data received in memory 1004 may optionally be storedon storage device 1008, either before or after execution by theprocessor 1002.

FIG. 11 illustrates a chip set or chip 1100 upon which an embodiment ofthe invention may be implemented. Chip set 1100 is programmed toinitiate a call using a multiple antenna system as described herein andincludes, for instance, the processor and memory components describedwith respect to FIG. 11 incorporated in one or more physical packages(e.g., chips). By way of example, a physical package includes anarrangement of one or more materials, components, and/or wires on astructural assembly (e.g., a baseboard) to provide one or morecharacteristics such as physical strength, conservation of size, and/orlimitation of electrical interaction. It is contemplated that in certainembodiments the chip set 1100 can be implemented in a single chip. It isfurther contemplated that in certain embodiments the chip set or chip1100 can be implemented as a single “system on a chip.” It is furthercontemplated that in certain embodiments a separate ASIC would not beused, for example, and that all relevant functions as disclosed hereinwould be performed by a processor or processors. Chip set or chip 1100,or a portion thereof, constitutes a means for performing one or moresteps of providing user interface navigation information associated withthe availability of functions. Chip set or chip 1100, or a portionthereof, constitutes a means for performing one or more steps ofdistributing notifications from developers to installed applications viaa notification enabler separate from the applications.

In one embodiment, the chip set or chip 1100 includes a communicationmechanism such as a bus 1101 for passing information among thecomponents of the chip set 1100. A processor 1103 has connectivity tothe bus 1101 to execute instructions and process information stored in,for example, a memory 1105. The processor 1103 may include one or moreprocessing cores with each core configured to perform independently. Amulti-core processor enables multiprocessing within a single physicalpackage. Examples of a multi-core processor include two, four, eight, orgreater numbers of processing cores. Alternatively or in addition, theprocessor 1103 may include one or more microprocessors configured intandem via the bus 1101 to enable independent execution of instructions,pipelining, and multithreading. The processor 1103 may also beaccompanied with one or more specialized components to perform certainprocessing functions and tasks such as one or more digital signalprocessors (DSP) 1107, or one or more application-specific integratedcircuits (ASIC) 1109. A DSP 1107 typically is configured to processreal-world signals (e.g., sound) in real time independently of theprocessor 1103. Similarly, an ASIC 1109 can be configured to performedspecialized functions not easily performed by a more general purposeprocessor. Other specialized components to aid in performing theinventive functions described herein may include one or more fieldprogrammable gate arrays (FPGA), one or more controllers, or one or moreother special-purpose computer chips.

In one embodiment, the chip set or chip 1100 includes merely one or moreprocessors and some software and/or firmware supporting and/or relatingto and/or for the one or more processors.

The processor 1103 and accompanying components have connectivity to thememory 1105 via the bus 1101. The memory 1105 includes both dynamicmemory (e.g., RAM, magnetic disk, writable optical disk, etc.) andstatic memory (e.g., ROM, CD-ROM, etc.) for storing executableinstructions that when executed perform the inventive steps describedherein to distribute notifications from developers to installedapplications via a notification enabler separate from the applications.The memory 1105 also stores the data associated with or generated by theexecution of the inventive steps.

FIG. 12 is a diagram of exemplary components of a mobile terminal (e.g.,handset) for communications, which is capable of operating in the systemof FIG. 1, according to one embodiment. In some embodiments, mobileterminal 1201, or a portion thereof, constitutes a means for performingone or more steps of distributing notifications from developers toinstalled applications via a notification enabler separate from theapplications. Generally, a radio receiver is often defined in terms offront-end and back-end characteristics. The front-end of the receiverencompasses all of the Radio Frequency (RF) circuitry whereas theback-end encompasses all of the base-band processing circuitry. As usedin this application, the term “circuitry” refers to both: (1)hardware-only implementations (such as implementations in only analogand/or digital circuitry), and (2) to combinations of circuitry andsoftware (and/or firmware) (such as, if applicable to the particularcontext, to a combination of processor(s), including digital signalprocessor(s), software, and memory(ies) that work together to cause anapparatus, such as a mobile phone or server, to perform variousfunctions). This definition of “circuitry” applies to all uses of thisterm in this application, including in any claims. As a further example,as used in this application and if applicable to the particular context,the term “circuitry” would also cover an implementation of merely aprocessor (or multiple processors) and its (or their) accompanyingsoftware/or firmware. The term “circuitry” would also cover ifapplicable to the particular context, for example, a baseband integratedcircuit or applications processor integrated circuit in a mobile phoneor a similar integrated circuit in a cellular network device or othernetwork devices.

Pertinent internal components of the telephone include a Main ControlUnit (MCU) 1203, a Digital Signal Processor (DSP) 1205, and areceiver/transmitter unit including a microphone gain control unit and aspeaker gain control unit. A main display unit 1207 provides a displayto the user in support of various applications and mobile terminalfunctions that perform or support the steps of distributingnotifications from developers to installed applications via anotification enabler separate from the applications. The display 1207includes display circuitry configured to display at least a portion of auser interface of the mobile terminal (e.g., mobile telephone).Additionally, the display 1207 and display circuitry are configured tofacilitate user control of at least some functions of the mobileterminal. An audio function circuitry 1209 includes a microphone 1211and microphone amplifier that amplifies the speech signal output fromthe microphone 1211. The amplified speech signal output from themicrophone 1211 is fed to a coder/decoder (CODEC) 1213.

A radio section 1215 amplifies power and converts frequency in order tocommunicate with a base station, which is included in a mobilecommunication system, via antenna 1217. The power amplifier (PA) 1219and the transmitter/modulation circuitry are operationally responsive tothe MCU 1203, with an output from the PA 1219 coupled to the duplexer1221 or circulator or antenna switch, as known in the art. The PA 1219also couples to a battery interface and power control unit 1220.

In use, a user of mobile terminal 1201 speaks into the microphone 1211and his or her voice along with any detected background noise isconverted into an analog voltage. The analog voltage is then convertedinto a digital signal through the Analog to Digital Converter (ADC)1223. The control unit 1203 routes the digital signal into the DSP 1205for processing therein, such as speech encoding, channel encoding,encrypting, and interleaving. In one embodiment, the processed voicesignals are encoded, by units not separately shown, using a cellulartransmission protocol such as enhanced data rates for global evolution(EDGE), general packet radio service (GPRS), global system for mobilecommunications (GSM), Internet protocol multimedia subsystem (IMS),universal mobile telecommunications system (UMTS), etc., as well as anyother suitable wireless medium, e.g., microwave access (WiMAX), LongTerm Evolution (LTE) networks, code division multiple access (CDMA),wideband code division multiple access (WCDMA), wireless fidelity(WiFi), satellite, and the like, or any combination thereof.

The encoded signals are then routed to an equalizer 1225 forcompensation of any frequency-dependent impairments that occur duringtransmission though the air such as phase and amplitude distortion.After equalizing the bit stream, the modulator 1227 combines the signalwith a RF signal generated in the RF interface 1229. The modulator 1227generates a sine wave by way of frequency or phase modulation. In orderto prepare the signal for transmission, an up-converter 1231 combinesthe sine wave output from the modulator 1227 with another sine wavegenerated by a synthesizer 1233 to achieve the desired frequency oftransmission. The signal is then sent through a PA 1219 to increase thesignal to an appropriate power level. In practical systems, the PA 1219acts as a variable gain amplifier whose gain is controlled by the DSP1205 from information received from a network base station. The signalis then filtered within the duplexer 1221 and optionally sent to anantenna coupler 1235 to match impedances to provide maximum powertransfer. Finally, the signal is transmitted via antenna 1217 to a localbase station. An automatic gain control (AGC) can be supplied to controlthe gain of the final stages of the receiver. The signals may beforwarded from there to a remote telephone which may be another cellulartelephone, any other mobile phone or a land-line connected to a PublicSwitched Telephone Network (PSTN), or other telephony networks.

Voice signals transmitted to the mobile terminal 1201 are received viaantenna 1217 and immediately amplified by a low noise amplifier (LNA)1237. A down-converter 1239 lowers the carrier frequency while thedemodulator 1241 strips away the RF leaving only a digital bit stream.The signal then goes through the equalizer 1225 and is processed by theDSP 1205. A Digital to Analog Converter (DAC) 1243 converts the signaland the resulting output is transmitted to the user through the speaker1245, all under control of a Main Control Unit (MCU) 1203 which can beimplemented as a Central Processing Unit (CPU).

The MCU 1203 receives various signals including input signals from thekeyboard 1247. The keyboard 1247 and/or the MCU 703 in combination withother user input components (e.g., the microphone 1211) comprise a userinterface circuitry for managing user input. The MCU 1203 runs a userinterface software to facilitate user control of at least some functionsof the mobile terminal 1201 to distribute notifications from developersto installed applications via a notification enabler separate from theapplications. The MCU 1203 also delivers a display command and a switchcommand to the display 1207 and to the speech output switchingcontroller, respectively. Further, the MCU 1203 exchanges informationwith the DSP 1205 and can access an optionally incorporated SIM card1249 and a memory 1251. In addition, the MCU 1203 executes variouscontrol functions required of the terminal. The DSP 1205 may, dependingupon the implementation, perform any of a variety of conventionaldigital processing functions on the voice signals. Additionally, DSP1205 determines the background noise level of the local environment fromthe signals detected by microphone 1211 and sets the gain of microphone1211 to a level selected to compensate for the natural tendency of theuser of the mobile terminal 1201.

The CODEC 1213 includes the ADC 1223 and DAC 1243. The memory 1251stores various data including call incoming tone data and is capable ofstoring other data including music data received via, e.g., the globalInternet. The software module could reside in RANI memory, flash memory,registers, or any other form of writable storage medium known in theart. The memory device 1251 may be, but not limited to, a single memory,CD, DVD, ROM, RAM, EEPROM, optical storage, magnetic disk storage, flashmemory storage, or any other non-volatile storage medium capable ofstoring digital data.

An optionally incorporated SIM card 1249 carries, for instance,important information, such as the cellular phone number, the carriersupplying service, subscription details, and security information. TheSIM card 1249 serves primarily to identify the mobile terminal 1201 on aradio network. The card 1249 also contains a memory for storing apersonal telephone number registry, text messages, and user specificmobile terminal settings.

While the invention has been described in connection with a number ofembodiments and implementations, the invention is not so limited butcovers various obvious modifications and equivalent arrangements, whichfall within the purview of the appended claims. Although features of theinvention are expressed in certain combinations among the claims, it iscontemplated that these features can be arranged in any combination andorder.

What is claimed is:
 1. A method comprising: determining by a processorat least one application installed on at least one device, wherein theat least one application is different from the one or more programs;determining by the processor one or more notification channelsassociated with the at least one application; registering by theprocessor the least one application to the one or more notificationchannels; and routing by the processor of one or more messages over theone or more notification channels based, at least in part, on theregistration.
 2. A method of claim 1, further comprising: determiningone or more initial messages routed to the at least one application, theat least one device, or combination thereof.
 3. A method of claim 2,further comprising: determining to present the one or more initialmessages in a notification user interface associated with a notificationenabler of the at least one device.
 4. A method of claim 3, furthercomprising: requesting preference information associated with the one ormore initial messages; and determining to present one or more subsequentmessages in the notification user interface based, at least in part, onthe preference information, and wherein the preference information isbased on interactions with one or more notifications received from theat least one device.
 5. A method of claim 1, further comprising:receiving the one or more messages to be carried on the one or morenotification channels via a console interface presented to one or morepublishers associated with the at least one application.
 6. A method ofclaim 5, wherein the console interface includes, at least in part, a webconsole interface that is separate from one or more application serversassociated with the at least one application.
 7. A method of claim 5,further comprising: identifying the at least one application, the one ormore publishers associated with the at least one application, or acombination thereof through at least one application store; and creatingthe one or more notification channels based, at least in part, theidentification.
 8. A method of claim 7, further comprising: validatingthe one or more publishers based, at least in part, on the identifying,the at least one application store, or a combination thereof, whereinthe creating the one or more notification channels is further based, atleast in part, on the validation.
 9. A method of claim 7, furthercomprising: associating one or more contextual criteria with the one ormore notification channels.
 10. A method of claim 9, wherein the routingone or more messages over the one or more notification channels isbased, at least in part, on whether contextual information associatedwith the at least one device, the at least one application, or acombination thereof substantially meets the one or more contextualcriteria.
 11. An apparatus comprising: at least one processor; and atleast one memory including computer program code for one or moreprograms, the at least one memory and the computer program codeconfigured to, with the at least one processor, cause the apparatus toperform at least the following, cause a determination of at least oneapplication installed on at least one device, wherein the at least oneapplication is different from the one or more programs; cause adetermination of one or more notification channels associated with theat least one application; cause a registration of the least oneapplication to the one or more notification channels; and cause arouting of one or more messages over the one or more notificationchannels based, at least in part, on the registration.
 12. An apparatusof claim 11, wherein the apparatus is further caused to: cause adetermination of one or more initial messages routed to the at least oneapplication, the at least one device, or combination thereof.
 13. Anapparatus of claim 12, wherein the apparatus is further caused to: causea determination to present the one or more initial messages in anotification user interface associated with a notification enabler ofthe at least one device.
 14. An apparatus of claim 13, wherein theapparatus is further caused to: cause a request for preferenceinformation associated with the one or more initial messages; and causea determination to present one or more subsequent messages in thenotification user interface based, at least in part, on the preferenceinformation, and wherein the preference information is based oninteractions with one or more notifications received from the at leastone device.
 15. An apparatus of claim 11, wherein the apparatus isfurther caused to: cause a reception of the one or more messages to becarried on the one or more notification channels via a console interfacepresented to one or more publishers associated with the at least oneapplication.
 16. An apparatus of claim 15, wherein the console interfaceincludes, at least in part, a web console interface that is separatefrom one or more application servers associated with the at least oneapplication.
 17. An apparatus of claim 15, wherein the apparatus isfurther caused to: cause an identification of the at least oneapplication, the one or more publishers associated with the at least oneapplication, or a combination thereof through at least one applicationstore; and cause a creation of the one or more notification channelsbased, at least in part, the identification.
 18. A method of claim 17,further comprising: cause a validation of the one or more publishersbased, at least in part, on the identifying, the at least oneapplication store, or a combination thereof, wherein the creation of theone or more notification channels is further based, at least in part, onthe validation.
 19. A method of claim 17, further comprising: cause anassociation of one or more contextual criteria with the one or morenotification channels.
 20. An apparatus of claim 19, wherein the routingone or more messages over the one or more notification channels isbased, at least in part, on whether contextual information associatedwith the at least one device, the at least one application, or acombination thereof substantially meets the one or more contextualcriteria.